Update diagnostic-settings.md #185
Conversation
Adding update to reflect the following known issue and considerations to avoid unexpected billing due loop ingestion issues. From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data. This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK
|
@miguel-parada : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
azure-monitor/svc
Change sent to author
platform/subsvc
labels
|
Learn Build status updates of commit 4da0538: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
@bwren Could you review this proposed update to your article and enter Thanks! |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds a warning to the diagnostic settings documentation about potential infinite loop scenarios when configuring Azure Storage accounts or Event Hub namespaces as destinations for their own diagnostic logs. The warning informs users that while the Azure portal prevents this configuration by design, it can still be accomplished through other tools like PowerShell, CLI, REST API, or ARM templates if needed.
Key Changes
- Added a new WARNING callout explaining the restriction on self-referential diagnostic settings
- Documented the billing and operational risks associated with circular log ingestion
- Clarified that the restriction is portal-specific and can be bypassed through other Azure tools
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| > Delete any diagnostic settings for a resource if you delete or rename that resource, or if you migrate it across resource groups or subscriptions. If the diagnostic setting isn't removed and this resource is recreated, any diagnostic settings for the deleted resource could be applied to the new one. This would resume the collection of resource logs as defined in the diagnostic setting. | ||
| > [!WARNING] | ||
| > From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. |
There was a problem hiding this comment.
Remove 'From' at the beginning of the sentence or rephrase. Suggested: 'In the Azure portal, when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you will be unable to select itself as a destination for the resource logs or metrics data.'
| > From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. | |
| > In the Azure portal, when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you will be unable to select itself as a destination for the resource logs or metrics data. |
Copilot uses AI. Check for mistakes.
| > [!WARNING] | ||
| > From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. | ||
| > This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data. | ||
| > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK. |
There was a problem hiding this comment.
This run-on sentence should be split for better readability. Suggested: 'This design is only applied at the Azure portal UX layer. If there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template, or other supported Microsoft SDKs.'
| > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK. | |
| > This design is only applied at the Azure portal UX layer. If there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template, or other supported Microsoft SDKs. |
Copilot uses AI. Check for mistakes.
| > [!WARNING] | ||
| > From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. | ||
| > This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data. | ||
| > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK. |
There was a problem hiding this comment.
Missing comma before 'or' in the list. Should be 'ARM Template, or other supported Microsoft SDKs' (also note 'SDK' should be pluralized to 'SDKs').
| > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK. | |
| > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template, or other supported Microsoft SDKs. |
Copilot uses AI. Check for mistakes.
|
Can you review this old PR and determine whether it needs to be closed or merged? @MicrosoftDocs/public-repo-pr-review-team |
github-actions
bot
removed
the
inactive
3 participants
Adding update to reflect the following known issue and considerations to avoid unexpected billing due loop ingestion issues.
From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data. This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK